Miles Sound System SDK 7.2a

Call Logging under Win32

Discussion

Miles contains a powerful diagnostic feature that allows developers to create a timestamped list of all of their application's foreground Miles calls, along with their parameters and results. The call log will be sent to an application callback routine registered with AIL_register_trace_callback, or to a plain text file if no debug-trace callback function has been registered by the application.

To take advantage of MSS's built-in logging without the need to recompile your application, you can create an "[MSS]" section in WIN.INI, followed by a string of the form, "MSSDebug=filename.txt". During execution of all subsequent Miles calls, a timestamped API call log will be written to the specified file.

For example, to dump the API call log to a file name foo.txt, add the following lines to WIN.INI:

[MSS]
MSSDebug=foo.txt

You can also view MSS's internal function calls by adding an extra line reading, "MSSSysDebug=1".

Next Topic (Miles Examples for Win32)

Previous Topic (Sharing the CPU under Win32)

Group: Overview for Win32: Miles on Windows XP, Vista, 2000, NT and Win9x
Related Functions: AIL_register_trace_callback
Related FAQs: My application is crashing - what should I try?, Where is the Miles source code? How can I rebuild it (in debug mode)?